1.1.1 -- January 21st, 1999. The following items were added, changed, or fixed:
• Modified the routine which inserts cache lines into a file which previously did not contain them. NCCC now does a full-length text compare (using CompareText) for the insertion point instead of an ASCII string compare. There was a fairly rare situation where the ASCII string compare could result in the download directory preference line being truncated. Because of the encryption Netscape uses to mask the actual location of the the disk cache and download directories, these lines could be longer than 255 characters.
• Throttled back the version check for the Appearance Manager. NavCom Cache Control now runs on any system which can support the Appearance Manager, System 8 included.
1.1 -- January 20th, 1999. The following items were added, changed, and fixed:
• Auto-find is b-a-a-a-a-c-k! Instead of kludging around with FSMakeFSSpec calls to figure out which directories existed, I took matters into my own hands with PBGetCatInfo. NCCC now looks for "Netscape ƒ" and "Netscape Users" in the Preferences folder of the startup drive. If it finds either of them, it will do a recursive search for Netscape Preferences files, using the following criteria:
File name: "Netscape Preferences"
Creator: "MOSS"
File type: "pref"
Data fork length > 0
If more then one file meeting those criteria exists, NCCC gives users a dialog box to select the file they want to work with. If no files are found, NCCC will let users know, and give them the option to manually search for the files. If only one file is found, it is loaded and the cache options dialog is presented.
• NCCC now scans the Netscape Preferences data before doing anything with it. The scan checks for 1.) at least one well-formed preference line, and 2.) properly terminated lines. If problems are found in either of these areas, the user is warned and given the choice to continue (at their own risk) or quit.
• Fixed a major brain fart in the routine that parses the preferences data prior to saving the new file. In certain degenerate cases, NCCC would hang while trying to find a location for the cache lines in the new preferences file. My analysis indicates that this occurs in preference files which are not well-formed, or are empty (i.e., were corrupt or orphaned). In any event, NCCC doesn't lock up in these situations anymore. The screening mentioned above should help, too.
• Compartmentalized the code considerably, cutting the number of data-related globals down to three. It should be much easier to debug and maintain in the future.
1.0.2 -- January 15th, 1999. The following items were added, changed, and fixed:
• Removed the auto-find feature (bug?). With Communicator's use of individual user profile folders, the auto-find process became quite complex and error-prone (i.e., this was the likely cause of the silent termination problem). Auto-find may return, but only after I've worked out all its kinks.
• Simplified the routine which checks for the presence of Appearance Manager. I thought this might have been a cause of silent termination. It wasn't, but I cleaned things up anyway.
1.0.1 -- January 14, 1999. The following items were added, changed, and fixed:
• Modified startup routines to allow manual file selection when the Netscape Preferences file can't be found in the standard path.
• Refined the logic in the initialization routines to clarify error conditions. This will, I hope, address the silent termination issue noted above.
